Release 10.1A: OpenEdge Application Server:
Developing AppServer Applications

Handling the STOP condition

If a client application raises the STOP condition while a remote procedure is active on a connected AppServer, OpenEdge also raises the STOP condition in the context of the AppServer agent handling the remote procedure request.

Note: A client can raise the STOP condition in the context of an executing remote procedure by invoking the STOP( ) method on the server object handle.

A STOP condition raised within a remote procedure does not necessarily terminate procedure execution, and it never causes the AppServer session to restart (as in a Progress 4GL client session). You can use the ON STOP statement within the remote procedure to intercept any STOP condition raised during execution and handle it as your application requires. Otherwise, the STOP condition propagates to the client application. For information on unhandled STOP conditions, see the "Effects of unhandled conditions" section.

A STOP condition raised in an Activate procedure for a stateless AppServer session has the same effect as if it were raised in the remote procedure for the request.